home *** CD-ROM | disk | FTP | other *** search
/ Cre@te Online 2000 December / Cre@teOnline CD05.iso / MacSoft / XML Authority.sea / XML Authority / Required / Samples / PIF-XML / pif-sample.xml next >
Encoding:
Extensible Markup Language  |  2000-05-03  |  9.5 KB  |  245 lines  |  [TEXT/CWIE]

  1. <?xml version="1.0"?>
  2. <!DOCTYPE pif SYSTEM "http://www.xmls.com/pif/pif.dtd">
  3.  
  4. <!-- this example based on http://ccs.mit.edu/pif8.html -->
  5. <!-- also see http://www.xmls.com/pif/ -->
  6.    
  7. <pif>
  8.  
  9. <!-- Project and team definitions -->
  10.  
  11. <activity id="EXAMPLE-PROJECT">
  12.   <documentation>A project is the top level activity of this activity elaboration hierarchy. The component attribute lists the subactivities of the project.</documentation>
  13.   <name>The Example Project Process</name>
  14.   <component href="ARCHITECTURE-DESIGN-1"/>
  15.   <component href="ELECTRICAL-DESIGN-2"/>
  16.   <component href="MECHANICAL-DESIGN-3"/>
  17.   <component href="DESIGN-REVIEW-4"/>
  18.   </activity>
  19.  
  20. <agent id="DESIGN-TEAM-1">
  21.   <documentation>A project team is composed of AGENTS, which as a whole can be viewed as an AGENT itself.</documentation>
  22.   <name>Project Design Team</name>
  23.   <component href="ARCHITECT-1"/>
  24.   <component href="ELECTRICAL-ENGINEER-2"/>
  25.   <component href="MECHANICAL-ENGINEER-3"/>
  26.   <component href="PROJECT-MANAGER-4"/>
  27.   </agent>
  28.  
  29. <performs id="TEAM-PERFORMS-PROJECT">
  30.   <actor href="DESIGN-TEAM-1"/>
  31.   <activity-ref href="EXAMPLE-PROJECT"/>
  32.   </performs>
  33.  
  34. <!-- Architectural design and Architect-1 -->
  35.  
  36. <activity id="ARCHITECTURE-DESIGN-1">
  37.   <documentation>This is the first activity of the example project. It starts when a contract is made. It produces an architectural design which will be followed by electrical and mechanical design.</documentation>
  38.   <name>Architecture Design</name>
  39.   <end href="ARCHITECTURE-DESIGN-1-END-TIMEPOINT"/>
  40.   </activity>
  41.  
  42. <timepoint id="ARCHITECTURE-DESIGN-1-END-TIMEPOINT">
  43.   <documentation>The end TIMEPOINT of the ARCHITECTURE-DESIGN-1 activity, among other things.</documentation>
  44.   <name>End Timepoint for Architecture Design</name>
  45.   </timepoint>
  46.  
  47. <agent id="ARCHITECT-1">
  48.   <name>Robert Callahan</name>
  49.   <capability href="ARCHITECTURE-SKILL"/>
  50.   </agent>
  51.  
  52. <performs id="PERFORMS-1">
  53.   <actor href="ARCHITECT-1"/>
  54.   <activity-ref href="ARCHITECTURE-DESIGN-1"/>
  55.   </performs>
  56.  
  57. <!-- Electrical Design and Electrical-Engineer-2 -->
  58.  
  59. <activity id="ELECTRICAL-DESIGN-2">
  60.   <documentation>This is the second activity of the project. This activity can begin only after ARCHITECTURE-DESIGN-1 is completed. It can (but does not necessarily) occur in parallel with MECHANICAL-DESIGN-3.</documentation>
  61.   <name>Electrical Design</name>
  62.   <begin href="ELECTRICAL-DESIGN-2-BEGIN-TIMEPOINT"/>
  63.   <end href="ELECTRICAL-DESIGN-2-END-TIMEPOINT"/>
  64.   </activity>
  65.  
  66. <timepoint id="ELECTRICAL-DESIGN-2-BEGIN-TIMEPOINT">
  67.   <documentation>The begin TIMEPOINT of the ELECTRICAL-DESIGN-2 activity, among other things</documentation>
  68.   <name>Begin Timepoint for ELECTRICAL-DESIGN-2</name>
  69.   </timepoint>
  70.  
  71. <timepoint id="ELECTRICAL-DESIGN-2-END-TIMEPOINT">
  72.   <documentation>The end timepoint of the ELECTRICAL-DESIGN-2 activity, among other things</documentation>
  73.   <name>End Timepoint for ELECTRICAL-DESIGN-2</name>
  74.   </timepoint>
  75.  
  76. <before id="ARCH-BEFORE-ELECTRIC">
  77.   <preceding-timepoint href="ARCHITECTURE-DESIGN-1-END-TIMEPOINT"/>
  78.   <succeeding-timepoint href="ELECTRICAL-DESIGN-2-BEGIN-TIMEPOINT"/>
  79.   </before>
  80.  
  81. <agent id="ELECTRICAL-ENGINEER-2">
  82.   <documentation>This engineer has two skills, one is electrical and the other is mechanical.  She is responsible for both electrical design and design review.</documentation>
  83.   <name>Cristina Marconi</name>
  84.   <capability href="ELECTRICAL-SKILL"/>  
  85.   <capability href="MECHANICAL-SKILL"/>
  86.   </agent>
  87.  
  88. <performs id="PERFORMS-2">
  89.   <actor href="ELECTRICAL-ENGINEER-2"/>
  90.   <activity-ref href="ELECTRICAL-DESIGN-2"/> 
  91.   </performs>
  92.  
  93. <!-- Mechanical Design Mechanical-Engineer-3 -->
  94.  
  95. <decision id="IF-ARCHITECTURE-DESIGN-1-DELAYED">
  96.   <documentation>The activity that decides what to do after checking if ARCHITECTURE-DESIGN-1 is delayed or not.</documentation>
  97.   <begin href="IF-ARCHITECTURE-DESIGN-DELAYED-BEGIN-TIMEPOINT"/> 
  98.   <if language="JavaScript">
  99.     <!-- script should go here -->
  100.     <component href="ARCHITECTURE-DESIGN-1-DELAYED"/>
  101.     <!-- the question remains how to best create PIF-SENTENCES in XML-->
  102.     </if>
  103.   <then href="MECHANICAL-DESIGN-4"/>
  104.   <else href="MECHANICAL-DESIGN-3"/>
  105.   </decision>
  106.  
  107. <activity-status id="ARCHITECTURE-DESIGN-1-DELAYED">
  108.   <documentation>The ARCHITECTURE-DESIGN-1 is delayed at the beginning of the DECISION activity, IF-ARCHITECTURE-DESIGN-DELAYED</documentation>
  109.   <activity-ref href="ARCHITECTURE-DESIGN-1"/>
  110.   <status>DELAYED</status>
  111.   <when href="IF-ARCHITECTURE-DESIGN-DELAYED-BEGIN-TIMEPOINT"/>
  112.   </activity-status>
  113.  
  114. <timepoint id="IF-ARCHITECTURE-DESIGN-DELAYED-BEGIN-TIMEPOINT">
  115.   <documentation>The begin timepoint of the IF-ARCHITECTURE-DESIGN-DELAYED activity</documentation>
  116.   <name>Begin Timepoint for IF-ARCHITECTURE-DESIGN-DELAYED</name>
  117.   </timepoint>
  118.  
  119. <activity id="MECHANICAL-DESIGN-3">
  120.   <documentation>This activity can begin only if ARCHITECTURE-DESIGN-1 is completed in time.  It can (but not necessarily) occur in parallel with ELECTRICAL-DESIGN-2.</documentation>
  121.   <name>Mechanical Design</name>
  122.   <begin href="MECHANICAL-DESIGN-3-BEGIN-TIMEPOINT"/>
  123.   <end href="MECHANICAL-DESIGN-3-END-TIMEPOINT"/> 
  124.   </activity>
  125.  
  126. <timepoint id="MECHANICAL-DESIGN-3-BEGIN-TIMEPOINT">
  127.   <documentation>The begin timepoint of the MECHANICAL-DESIGN-3 activity, among other things</documentation>
  128.   <name>Begin Timepoint for Mechanical Design 3</name>
  129.   </timepoint>
  130.  
  131. <timepoint id="MECHANICAL-DESIGN-3-END-TIMEPOINT">
  132.   <documentation>The End timepoint of the MECHANICAL-DESIGN-3 activity, among other things</documentation>
  133.   <name>End Timepoint for Mechanical Design 3</name>
  134.   </timepoint>
  135.  
  136.  
  137. <activity id="MECHANICAL-DESIGN-4">
  138.   <documentation>This activity can begin only if ARCHITECTURE-DESIGN-1 is delayed.  It can (but not necessarily) occur in parallel with ELECTRICAL-DESIGN-2.</documentation>
  139.   <name>Mechanical Design 4</name>
  140.   <begin href="MECHANICAL-DESIGN-4-BEGIN-TIMEPOINT"/>
  141.   <end href="MECHANICAL-DESIGN-4-END-TIMEPOINT"/>
  142.   </activity>
  143.  
  144. <timepoint id="MECHANICAL-DESIGN-4-BEGIN-TIMEPOINT">
  145.   <documentation>The begin TIMEPOINT of the MECHANICAL-DESIGN-4 activity, among other things</documentation>
  146.   <name>Begin Timepoint for Mechanical Design 4</name>
  147.   </timepoint>
  148.  
  149. <timepoint id="MECHANICAL-DESIGN-4-END-TIMEPOINT">
  150.   <documentation>The End Timepoint of the MECHANICAL-DESIGN-4 activity, among other things</documentation>
  151.   <name>End Timepoint for Mechanical Design 4</name>
  152.   </timepoint>
  153.  
  154. <before id="ARCHITECTURE-DESIGN-1-BEFORE-MECHANICAL-DESIGN-3">
  155.   <preceding-timepoint href="ARCHITECTURE-DESIGN-1-END-TIMEPOINT"/>
  156.   <succeeding-timepoint href="MECHANICAL-DESIGN-3-BEGIN-TIMEPOINT"/>
  157.   </before>
  158.  
  159. <before id="ARCHITECTURE-DESIGN-1-BEFORE-MECHANICAL-DESIGN-4">
  160.   <preceding-timepoint href="ARCHITECTURE-DESIGN-1-END-TIMEPOINT"/>
  161.   <succeeding-timepoint href="MECHANICAL-DESIGN-4-BEGIN-TIMEPOINT"/>
  162.   </before>
  163.  
  164. <entity id="MECHANICAL-SKILL">
  165.   <name>Mechanical Skill</name>
  166.   </entity>
  167.  
  168. <entity id="SPECIAL-MECHANICAL-SKILL">
  169.   <name>Special Mechanical Skill</name>
  170.   </entity>
  171.  
  172. <entity id="ELECTRICAL-SKILL">
  173.   <name>Electrical Skill</name>
  174.   </entity>
  175.  
  176. <entity id="MANAGEMENT-SKILL"> 
  177.   <name>Management Skill</name>
  178.   </entity>
  179.  
  180. <agent id="MECHANICAL-ENGINEER-3">
  181.   <name>Gary Fassbinder</name>
  182.   <capability href="MECHANICAL-SKILL"/>
  183.   </agent>
  184.  
  185. <performs id="PERFORMS-3">
  186.   <actor href="MECHANICAL-ENGINEER-3"/>
  187.   <activity-ref href="MECHANICAL-DESIGN-3"/>
  188.   </performs>
  189.  
  190. <!--Nobody has been assigned yet to the MECHANICAL-DESIGN-4, but whoever does it has to have the special-mechanical-skill-1. -->
  191. <performs id="PERFORMS-4">
  192.   <activity-ref href="MECHANICAL-DESIGN-4"/>
  193.   <constraint language="JavaScript">
  194.     <!-- script should go here -->
  195.     ?SELF.Actor.Capability SPECIAL-MECHANICAL-SKILL-1
  196.     <!-- the question remains how to best create PIF-SENTENCES in XML -->
  197.     </constraint>
  198.   </performs>
  199.  
  200. <!-- Design Review and Project Manager -->
  201. <activity id="DESIGN-REVIEW-5">
  202.   <documentation>This is the last activity of the project.  This activity can begin only after both ELECTRICAL-DESIGN-2 and MECHANICAL-DESIGN-3 (or MECHANICAL-DESIGN-4) are completed.  It has four responsible AGENTs, and this activity can be viewed as a design-review meeting.  All team members must participate.</documentation>
  203.   <name>Design Review</name>
  204.   <begin href="DESIGN-REVIEW-5-BEGIN-TIMEPOINT"/>
  205.   </activity>
  206.  
  207. <timepoint id="DESIGN-REVIEW-5-BEGIN-TIMEPOINT">
  208.   <documentation>The Begin timepoint of the DESIGN-REVIEW-5 activity, among other things</documentation>
  209.   <name>Begin Timepoint for Design Review 5</name>
  210.   </timepoint>
  211.  
  212. <before id="ELECTRICAL-BEFORE-DESIGN-REVIEW">
  213.  <preceding-timepoint href="ELECTRICAL-DESIGN-2-END-TIMEPOINT"/>
  214.  <succeeding-timepoint href="DESIGN-REVIEW-5-BEGIN-TIMEPOINT"/>
  215.  </before> 
  216.  
  217. <before id="MECHANICAL-3-BEFORE-DESIGN-REVIEW">
  218.  <preceding-timepoint href="MECHANICAL-DESIGN-3-END-TIMEPOINT"/>
  219.  <succeeding-timepoint href="DESIGN-REVIEW-5-BEGIN-TIMEPOINT"/>
  220.  </before>
  221.  
  222. <before id="MECHANICAL-4-BEFORE-DESIGN-REVIEW">
  223.   <preceding-timepoint href="MECHANICAL-DESIGN-4-END-TIMEPOINT"/>
  224.   <succeeding-timepoint href="DESIGN-REVIEW-5-BEGIN-TIMEPOINT"/>
  225.   </before>
  226.  
  227. <agent id="PROJECT-MANAGER-4">
  228.   <documentation>This AGENT is the manager of this project.  She is responsible for decision-making whenever a exception occurs during the process of the project.  She is also co-responsible for the design-review activity.</documentation>
  229.   <name>Ann Rollins</name>
  230.   <capability href="MECHANICAL-SKILL"/> 
  231.   <capability href="ELECTRICAL-SKILL"/> 
  232.   <capability href="MANAGEMENT-SKILL"/>
  233.   </agent>
  234.  
  235. <performs id="PERFORMS-5">
  236.   <agent href="DESIGN-TEAM-1"/>
  237.   <activity-ref href="DESIGN-REVIEW-5"/>
  238.   </performs>
  239.  
  240. </pif>
  241.  
  242.  
  243.  
  244.  
  245.